Clarify that package.order does not affect visibility#3923
Merged
HansOlsson merged 3 commits intoJul 3, 2026
Conversation
henrikt-ma
force-pushed
the
cleanup/package-order-visibility
branch
from
f53b16c to
f89c0c2
Compare
HansOlsson
reviewed
Jun 29, 2026
Collaborator
Author
|
I have added some additional clarifications, and in particular what this means for the ability to map a class to a separate file or directory. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addressing a small need for clarification encountered in relation to #3921.